Conversation
CodSpeed Performance ReportMerging #4984 will degrade performances by 6.67%Comparing Summary
Benchmarks breakdown
|
|
:) |
this file only gets copied during `reflex init`, so don't blow it away
There was a problem hiding this comment.
still a lot more to go on this, but i like the direction.
- internal nav without breaking websocket
- support dynamic routes (and hopefully translate existing syntax)
- pre-render HTML and use hydrateRoot
In the future it would also be awesome to expose an interface for devs to specify additional dynamic routes that should be pre-rendered.
Some grunt work to get the tests passing, but i think we should try to keep this branch up to date with main and try to move over as soon as its stable and has feature parity.
It would be nice if things were implemented in a way that would allow us to support both, but that kind of refactoring work is probably not something we can prioritize over the wins from simplifying and shrinking our frontend stack, so probably makes sense to just move fast at this point and hard cut away from next.
i was a bit stuck on these two, the code for them was very tied to nextjs way of doing things, so help there is appreciated
we do have an SSR option but i don't know how much it does there are also other things:
|
|
JSX syntax to JS syntax trnasformation seems to be done (we can in theory make that its own PR) |
…/script to make reflex web compile
|
reflex-chakra no longer working |
When the app specified custom `head_components`, the default meta was not being included.
When pushing an empty fragment onto react router, the page url does not actually change.
almost, usable, but needs to port 404, figure out titles and such, make sure events aren't broken, and bring back sitemap, among other things